Skip to content

[pull] main from bazel-contrib:main#526

Merged
pull[bot] merged 2 commits intogarymm:mainfrom
bazel-contrib:main
Feb 18, 2026
Merged

[pull] main from bazel-contrib:main#526
pull[bot] merged 2 commits intogarymm:mainfrom
bazel-contrib:main

Conversation

@pull
Copy link
Copy Markdown

@pull pull Bot commented Feb 18, 2026

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

Saish-3 and others added 2 commits February 18, 2026 00:53
…3602)

Adds documentation explaining:

- current_py_cc_headers
- current_py_cc_headers_abi3
- current_py_cc_libs

Describes how these targets expose headers and libraries
from the active Python C toolchain and clarifies that they
should be used instead of legacy alias targets when embedding
Python or building C extensions.

This addresses issue #3098.

---------

Co-authored-by: Richard Levasseur <rlevasseur@google.com>
…3601)

Update `remove_invalid_(binary|library)` gazelle tests.

These changes will make a little more sense in a followup PR that
finishes the "delete invalid targets" work started in #3046. In that PR,
I pushed back on changes that would mean `py_test` and `py_library`
targets got removed if they were invalid (see
#3046 (review)).

It's now time to fix that and make it so _any_ invalid target, not just
`py_binary`, is removed see
#3046 (comment)).
That change will come in a followup PR.

This PR updates tests by adding some always-valid targets and does some
light renaming of the targets.
@pull pull Bot locked and limited conversation to collaborators Feb 18, 2026
@pull pull Bot added the ⤵️ pull label Feb 18, 2026
@pull pull Bot merged commit d31ec0d into garymm:main Feb 18, 2026
2 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants